Create DevOps Gate Process

Overview

This document describes the procedure to set up a DevOps Gate process.

Create a New DevOps Gate Process

1. Navigate to the DevOps Gate page.
2. Press the Add DevOps Gate Process button.

Configure System Security with DevOps Gate

3. Open another browser tab and go to the Systems page.
4. Press the Edit button for the systems included in the DevOps process.
5. Select the preferred Webhook Security options:
   1. Restrict Webhooks to specific IP addresses.
   2. Allow anonymous webhook notifications for DevOps Gate or use a SyncNow username account for authenticating webhook requests.
6. Save the system configuration.

Using anonymous webhook notifications is not recommended and can be dangerous. We highly recommend setting the origin IP address for the work systems from which webhooks are issued to SyncNow.

Configure the DevOps Gate Process

7. Set a name for the process.
8. Select the systems from which to receive webhooks and the target system where entities will be updated.
9. Add unique system prefixes. These prefixes will help the service recognize the source system and identify which entity should be updated.
10. Select allowed target sub-projects. Only entities from allowed projects will be created or updated, and comments will only be added to entities from these sub-projects.
11. Select the action: Create, Update, or Upload Attachments.
12. Press the Save button.

A new DevOps Gate Process has been created.

Set DevOps Gate Process Mapping

13. Press the Mapping Entities button.
14. Add entity pairs. On each API call, as many entities as defined in the mapping will be created or updated. System connectors without entities, such as Jenkins or Generic System (for API calls), allow mapping only SyncNow Virtual Entity to another target entity. Generic System and Jenkins can only be the source.

Field Mapping

15. Press the Mapping Fields button.

16. Add as many fields as needed. For Generic System, only SyncNow Virtual Field is available, but you can define fields with any names. Each name defines a parameter received from the source system side and mapped to the target field. Generic System and Jenkins can only be the source of the process.
17. Press the Save button.
18. Press the Edit Field button to open the dialog with advanced field definitions.
19. Set C# or constant data transformation for mapped fields if needed to any value received from systems.